Laravel 6.0 Shift #41
Conversation
The Laravel framework adopts the PSR-2 coding style with some additions. Laravel apps *should* adopt this coding style as well. However, Shift allows you to customize the adopted coding style through the [.shiftrc][1] file by using your [PHP CS Fixer][2] config. [1]: https://laravelshift.com/shiftrc-configuration-file [2]: https://github.com/FriendsOfPHP/PHP-CS-Fixer
In an effort to make upgrading the constantly changing config files easier, Shift defaulted them so you can review the commit diff for changes. Moving forward, you should use ENV variables or create a separate config file to allow the core config files to remain automatically upgradeable.
|
❌ Shift could not upgrade your HTTP Kernel because it differed from the default version. You will need to compare this file against the default Laravel 6.0 version and merge any changes. |
|
|
ℹ️ The Eloquent model's |
|
ℹ️ Laravel 6.0 made performance optimizations for integer key types. If you are using a string as your model's primary key, you may set the /**
* The "type" of the primary key ID.
*
* @var string
*/
protected $keyType = 'string'; |
|
ℹ️ The |
|
ℹ️ Previous versions of Laravel would retry jobs indefinitely. Beginning with Laravel 6.0, the |
|
🎉 Congratulations, you're now running the latest version of Laravel. The following Shifts can ensure your app is fully upgraded and following the practices recommended by Laravel and the community:
In addition, stay upgraded forever as well as run these Shifts by subscribing to one of the new Shifty Plans. |
This pull request includes the changes for upgrading to Laravel 6.0. Feel free to commit any additional changes to the
shift-17772branch.Before merging, you should:
shift-17772branchcomposer update(if the scripts fail, add--no-scripts)If you want help with your upgrade, check out the Shift Human Services or join the Shifty Coders Slack room to get answers to all your Laravel questions.